Generating a request from a nutraceutical inventory

ABSTRACT

A method, system, and computer program product are described for registering a nutraceutical-containing dispensation from an inventory and responding to the registering by indicating a request quantity partly based on the inventory and partly based on a consumption regimen.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is related to, claims the earliest availableeffective filing date(s) from (e.g., claims earliest available prioritydates for other than provisional patent applications; claims benefitsunder 35 USC § 119(e) for provisional patent applications), andincorporates by reference in its entirety all subject matter of thefollowing listed application(s) (the “Related Applications”) to theextent such subject matter is not inconsistent herewith; the presentapplication also claims the earliest available effective filing date(s)from, and also incorporates by reference in its entirety all subjectmatter of any and all parent, grandparent, great-grandparent, etc.applications of the Related Application(s) to the extent such subjectmatter is not inconsistent herewith. The United States Patent Office(USPTO) has published a notice to the effect that the USPTO's computerprograms require that patent applicants reference both a serial numberand indicate whether an application is a continuation or continuation inpart. Stephen G. Kunin, Benefit of Prior-Filed Application, USPTOElectronic Official Gazette, Mar. 18, 2003 athttp://www.uspto.gov/web/offices/com/sol/og/2003/week11/patbene.htm. Thepresent applicant entity has provided below a specific reference to theapplication(s) from which priority is being claimed as recited bystatute. Applicant entity understands that the statute is unambiguous inits specific reference language and does not require either a serialnumber or any characterization such as “continuation” or“continuation-in-part.” Notwithstanding the foregoing, applicant entityunderstands that the USPTO's computer programs have certain data entryrequirements, and hence applicant entity is designating the presentapplication as a continuation in part of its parent applications, butexpressly points out that such designations are not to be construed inany way as any type of commentary and/or admission as to whether or notthe present application contains any new matter in addition to thematter of its parent application(s).

Related Applications:

1. For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 11/283,548, entitled PROVIDING ASSISTANCE RELATEDTO HEALTH, naming Edward K. Y. Jung, Joyce A. Levien, Robert W. Lord,Mark A. Malamud, John D. Rinaldo, Jr., Clarence T. Tegreene and LowellL. Wood, Jr. as inventors, filed Nov. 17, 2005, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

2. For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 11/291,482, entitled TESTING-DEPENDENTADMINISTRATION OF A NUTRACEUTICAL, naming Edward K. Y. Jung, Royce A.Levien, Robert W. Lord, Mark A. Malamud, John D. Rinaldo, Jr., ClarenceT. Tegreene and Lowell L. Wood, Jr. as inventors, filed Nov. 30, 2005,which is currently co-pending, or is an application of which a currentlyco-pending application is entitled to the benefit of the filing date.

3. For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 11/291,532, entitled GENERATING A NUTRACEUTICALREQUEST FROM AN INVENTORY, naming Edward K. Y. Jung, Royce A. Levien,Robert W. Lord, Mark A. Malamud, John D. Rinaldo, Jr., Clarence T.Tegreene an dLowell L. Wood, Jr. as inventors, filed Nov. 30, 2005,which is currently co-pending, or is an application of which a currentlyco-pending application is entitled to the benefit of the filing date.

SUMMARY

An embodiment provides a method. In one implementation, the methodincludes but is not limited to registering a nutraceutical-containingdispensation from an inventory and responding to the registering byindicating a request quantity partly based on the inventory and partlybased on a consumption regimen. In addition to the foregoing, othercommunication method aspects are described in the claims, drawings, andtext forming a part of the present disclosure.

In one or more various aspects, related systems include but are notlimited to circuitry and/or programming for effecting the hereinreferenced method aspects; the circuitry and/or programming can bevirtually any combination of hardware, software, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to circuitry for registering anutraceutical-containing dispensation from an inventory and a module forresponding to the registering by indicating a request quantity partlybased on the inventory and partly based on a consumption regimen. Inaddition to the foregoing, other computer program product aspects aredescribed in the claims, drawings, and text forming a part of thepresent disclosure.

An embodiment provides another system. In one implementation, the othersystem includes but is not limited to a computing device and one or moreinstructions that when executed by the computing device cause thecomputing device to perform at least one of registering anutraceutical-containing dispensation from an inventory and respondingto the registering by indicating a request quantity partly based on theinventory and partly based on a consumption regimen. In addition to theforegoing, other computer program product aspects are described in theclaims, drawings, and text forming a part of the present disclosure.

An embodiment provides a computer program product. In oneimplementation, the computer program product includes but is not limitedto a signal-bearing medium bearing at least one of (a) one or moreinstructions for registering a nutraceutical-containing dispensationfrom an inventory and (b) one or more instructions for responding to theregistering by indicating a request quantity partly based on theinventory and partly based on a consumption regimen.

In addition to the foregoing, various other embodiments are set forthand described in the text (e.g., claims and/or detailed description)and/or drawings of the present description.

The foregoing is a summary and thus contains, by necessity,simplifications, generalizations and omissions of detail; consequently,those skilled in the art will appreciate that the summary isillustrative only and is not intended to be in any way limiting. Otheraspects, features, and advantages of the devices and/or processesdescribed herein, as defined by the claims, will become apparent in thedetailed description set forth herein.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 shows an operational flow representing example operations thatproduce an indication of an amount.

FIG. 2 shows an example system in schematic form, a hardwareimplementation able to perform variants of the flow of FIG. 1.

FIG. 3 shows another example system able to perform the flow of FIG. 1and many similar variations.

FIG. 4 shows another example system able to perform the flow of FIG. 1and many similar variations.

FIG. 5 shows various optional features of the flow of FIG. 1.

FIG. 6 shows another example system able to perform many variants of theabove-described flows.

FIG. 7 shows various optional features of the flow of FIG. 1 or 5.

FIG. 8 shows various optional features of the flow of FIG. 1, 5, or 7.

FIG. 9 shows further optional features of the system of FIG. 4.

FIG. 10 shows various optional features of the flow of FIG. 1, 5, 7 or8.

FIG. 11 shows a system that includes a signal-bearing medium that cancomprise or interact with a conduit, a disk, an integrated circuit, or acomputing device.

FIG. 12 shows other optional features of the above-described flows.

FIG. 13 shows still more optional features of the above-described flows.

FIG. 14 shows another example system embodiment in schematic form.

DETAILED DESCRIPTION

FIG. 14 shows user system 1400 comprising one or more of registrationlogic 1440 or quantity determination logic 1490. Quantity determinationlogic 1490 optionally comprises one or more of storage logic 1450, userinterface 1462, module update logic 1470, network interface 1492, orcompound identification logic 1496. Registration logic 1440 can includeone or more of dispensation confirmation logic 1443, user query logic1446, inventory maintenance logic 1447, event predictor 1448, regimenimplementation logic 1480, or scheduler 1483. Storage logic 1450 caninclude one or more of subject description 1453, user data 1454, regimendescription 1455, and electronic inventory 1456. User interface 1462 caninclude one or more of authentication logic 1466 or display 1467.Nutraceutical bin 1445 can contain one or more nutraceuticals (e.g.,nutraceutical-containing compounds) as well as medications and the like.Nutraceutical bin may comprise part of inventory manager 1444, or may besituated in a stand-alone position accessible to user 1460 or one ormore other users.

FIG. 1 shows an operational flow 100 representing example operationsthat produce an indication of an amount of a request quantity, such asby indicating a rate or otherwise expressing a quantity that includes anutraceutical. Flow 100 and other embodiments as described belowsystemize regimens that include one or more of these components,facilitating or enabling a user's implementation of a regimen.

After a start operation, operational flow 100 moves to operation 140,comprising registering a nutraceutical-containing dispensation from aninventory (e.g., registration logic 1440 receiving an indication thatuser 1460 has removed a certain quantity of nutraceutical fromnutraceutrical bin 1445). The dispensation can be a completeddispensation, an in-progress dispensation, a tentative dispensation, ascheduled dispensation, or a canceled dispensation of one or morenutraceutical-containing materials, for example. Likewise thedispensation can relate to electronic inventory 1456 or any physicalinventory. After operation 140, flow 100 then moves to operation 150,comprising responding to the registering by indicating a requestquantity partly based on the inventory and partly based on a consumptionregimen (e.g., quantity determination logic 1490 sending a requestquantity via network interface 1492—through network 1420—to suppliersystem 1425, where the request is partly based on a past or presentcontent of nutraceutical bin 1445 and a partly based on a past orpresent consumption regimen as indicated by regimen description 1455).The indication can be a display or other transmission, for example. Theconsumption regimen can optionally contain one or more regimens orregimen components, such as seasonal, interspersed, contingent,occasional, or other conditional regimen(s). Alternatively oradditionally, the consumption regimen can comprise a component of amaster regimen that also includes a non-consumption component. FIGS. 5,7, 8, 10, 12, and 13 below include many variations of operational flow100. In various embodiments such as these, of course, flow 100 caninclude additional operations or variations in the sequence ofoperations.

Referring now to FIG. 2, there is shown an example system 200 inschematic form, a hardware implementation able to perform variants offlow 100 as described below. Primary module 210 includes circuitry 230for receiving at least an indication of the registration (via linkage232, e.g.) of a state of a subject (an animal or other organism, e.g.).Primary module 210 further includes logic 240 (such as a processor orprogrammable logic, e.g.) for indicating the request quantity (viainterface 238, e.g.) partly based on the dispensation or other aspect ofthe inventory, and partly based on the consumption regimen. Primarymodule 210 can further include medium 250 accessible by at least logic240, as described below. (The dashed outline of medium 250 signifiesthat some embodiments are specifically contemplated to exclude thisfeature, and others are contemplated to include it.)

Linkage 232 is similarly indicated as optional. Even if system 200 ismerely a kit or physical structure with no communication linkage 232,for example, it can be advantageous for user 260 to access primarymodule 210 in proximity to inventory manager 280. Linkage 232 caninclude one or more of analog data, digital data, or a measurablephysical property such as a distance or similar geometry. Alternativelyor additionally, linkage 232 can comprise a conduit bearing one or moreinstructions that can be stored in medium 250, for example, or can beexecuted by logic 240 to perform one or more variations of flow 100 suchas those shown in FIG. 5, 7, 8, 10, 12, or 13. Alternatively oradditionally, information can be conveyed to primary module on a ticketor a similar printed record or memory device that can be deposited intoprimary module 210. Alternatively or additionally, circuitry 230 canreceive information (such as the regimen, e.g.) remotely and/or fromuser 260.

Inventory manager 280 includes a medication or other prescribedcomponent (C₁) 281, for example, and can include one or morenutraceutical-containing or other components (C₂) 282. Inventory manager280 can be accessible to user 260 via optional interface 262, which canoptionally be used for receiving user input in lieu of interface 238.Alternatively or additionally, interface 262 can comprise avending-machine-style dispenser able to dispense one or more of thecomponent(s) 281, 282 to user 260. Even in an embodiment in whichdispensations are via a third party, and in lieu of interface 262,primary module 210 can register the dispensation such as via linkage 232or interface 238, and respond accordingly (by operation 150, e.g.).

Referring now to FIG. 3, there is shown another example system 300 ableto perform operational flow 100 of FIG. 1 and many similar variations.System 300 includes circuitry 330 and logic 340 as described below, andcan further include one or more of link 321, interface 338, or medium350. Logic 340 can optionally receive input from a user (such as fromuser 360 via interface 338, e.g.) locally. Medium 350 can bear one ormore instructions that can be executed by logic 340 (optionally acomputing device, e.g.) for performing one or more of the flows of FIG.5, 7, 8, 10, 12, or 13.

As shown, link 321 can operably couple system 300 with network 320. Insome embodiments, network 320 can thus have access to online researchresource 312 through linkage 322 or to server 313 through linkage 323.Alternatively or additionally, network 320 can have access to expert 314through linkage 324 or to supplier 370 through linkage 327. (“Expert”314 can actually be an herbalist, a pharmacist, a physician, apsychologist, a parent, an author, a document, a database, a blog, orany other source of opinion or information.) Research resource 312 canbe remote from system 300 or from server 313, expert 314, or supplier370. Expert 314 can optionally be located at a clinic or similar retailor healthcare facility that can advantageously include system 300 aswell as one or more of online research resource 312, server 313,supplier 370, or user 360.

System 300 optionally includes circuitry (optionally circuitry 330 withlink 321, e.g.) for communicating with supplier 370 via network 320,such as by electronic mail, facsimile, or a similar digital format.Alternatively or additionally, circuitry 330 can coordinate with link321 for communicating with a regimen server (such as server 313, e.g.)or with a consultant (such as expert 314) remotely. Alternatively oradditionally, supplier 370 can be configured to communicate with expert314 via linkage 327 or with (another) user 360 via linkage 361.Alternatively or additionally, user 360 can access a component C₁ 381(and optionally one or more additional components C₂ 382) in aninventory manager 380 via interface 362.

In some embodiments, system 300 is a computer or similar device withinventory maintenance capabilities. In performing operation 140 (ofFIG. 1) or some variants described below, logic 340 can register adispensation from an inventory, for example by receiving an indicationof the dispensation via user interface 338. Circuitry 330 can respond asappropriate by indicating a request quantity (at operation 150, e.g.),such as by transmitting the request quantity via link 321 as an order(to supplier 370, e.g.) or as a validation request (to a physician orother expert 314, e.g.).

Referring now to FIG. 4, there is shown another example system 400 ableto perform operational flow 100 of FIG. 1 and many similar variationssuch as those of FIG. 5, 7, 8, 10, 12, or 13. System 400 comprisescircuitry 440 for registering a nutraceutical-containing dispensationfrom an inventory and module 470 for responding to the registering byindicating a request quantity partly based on the inventory and partlybased on a consumption regimen. Circuitry 440 can adjoin, overlap, orotherwise be operable to interact with module 470.

Module 470 optionally comprises circuitry 471 for determining therequest quantity partly based on a user preference. Alternatively oradditionally, module 470 can comprise one or more of circuitry 472 forimplementing the consumption regimen, medium 473 for storing at leastthe request quantity, circuitry 474 for confirming thenutraceutical-containing dispensation, or medium 475 bearing one or moreinstructions for generating the request quantity.

Also as shown, alternatively or additionally, system 400 can furthercomprise circuitry 481 for receiving at least a portion of theconsumption regimen remotely. Alternatively or additionally, system 400can further comprise circuitry 482 for identifying a compound comprisingthe request quantity, circuitry 483 for receiving a user preference,circuitry 484 for authenticating a user input, circuitry 485 forreceiving an update of the consumption regimen, or circuitry 486 forreceiving an update of the module for responding to the registering byindicating a request quantity.

Referring now to FIG. 5, there are shown various optional features ofoperational flow 100 of FIG. 1. Operation 140—registering anutraceutical-containing dispensation from an inventory—may include oneor more operations such as operation 543, which depicts confirming thenutraceutical-containing dispensation (e.g., dispensation confirmationlogic 1443 confirming that a user 1460 has removed about 6 grams of St.John's wort from nutraceutical bin 1445 over the course of a week, suchas, for example, dispensation confirmation logic 1443 comparing startingand ending volumes of St. John's wort in nutraceutical bin 1445).Operation 543 can likewise be performed by dispensation confirmationlogic 1443 receiving a user input affirming the dispensation, forexample, or by a module 470 that includes circuitry 474 of FIG. 4.

In various implementations, user system 1400 of FIG. 14 or system 400 ofFIG. 4 can alternatively or additionally be configured to performoperation 150—responding to the registering by indicating a requestquantity partly based on the inventory and partly based on a consumptionregimen—by including one or more of operation 551, operation 552,operation 556, operation 557, operation 558, or operation 560. Operation551 comprises receiving a user preference (e.g., user interface 1462receiving a preference from user 1460 that user 1460 desires ahigh-energy formulation of his regimen), such as can be performed by asystem 400 that includes circuitry 483 of FIG. 4.

Operation 552 comprises identifying a compound comprising the requestquantity (e.g., compound identification logic 1496 identifying anutraceutical such as bee pollen or ginkgo biloba). For example, if theelectronic inventory 1456 indicates that the nutraceutical bin 1445contains bee pollen and the user data 1454 indicates a preference for ahigh energy regimen, compound identification logic 1496 can identify beepollen as a desirable nutraceutical by updating regimen description1455. In other embodiments, operation 552 can be performed a variant ofsystem 400 that includes circuitry 482.

Operation 556 comprises determining the request quantity partly based ona user preference (e.g., quantity determination logic 1490 determiningthat user 1460 has requested one pound of a protein supplement inresponse to a user preference for one-month-based purchases). The userdata 1454 can also include one or more preferences relating tonutraceutical price, freshness and/or diversity, or the like. In otherembodiments, operation 556 can be performed by a module 470 thatincludes circuitry 471 of FIG. 4.

Operation 557 comprises receiving the request quantity (e.g., userinterface 1462 can receive data indicating a suggested amount of 50tablets of a vitamin B complex), which can then be displayed to user1460 or stored for later use, for example. In other embodiments, therequest quantity can likewise be received from module 470 afterexecuting the one or more instructions for generating the requestquantity borne by medium 475.

Operation 558 comprises storing the request quantity (e.g., userinterface 1462 storing a message in user data 1454 containing severalsuggested reorder amounts until user 1460 logs in again). In otherembodiments, operation 558 can be performed with medium 473 of FIG. 4 orwith medium 350 of FIG. 3. These or other media of system 400 canlikewise store data related to the request quantity, of course, such asother request quantities, medical history data, security information,supplier identification, user preferences, or instructions in light ofteachings herein.

Operation 560—performing one or more additional operations—may includeone or more of the following operations: 561, 562, 563, 564, and/or 566.Operation 561 depicts receiving an update of the consumption regimenremotely (e.g., network interface 1492 receiving an indication that agiven expert's diet regimen now allows up to 280 grams of proteinsupplement per week). This information can then be used by scheduler1483 or stored in regimen description 1455 for later display to user1460, for example.

Operation 562 depicts scheduling the consumption regimen (e.g.,scheduler 1483 using a received update in changing the current regimento allow at most 40 grams of protein per day). In other embodiments,operation 562 can be performed by a module 470 that includes circuitry472 of FIG. 4.

Operation 563 depicts receiving an update of a module (e.g., moduleupdate logic 1470 receiving version 2.7 of a data file relied upon bycompound identification logic 1496, and using it to replace version 2.8previously in effect). In other embodiments, operation 563 can beperformed by a system 400 that includes circuitry 486 of FIG. 4.

Operation 564 depicts receiving at least a portion of the consumptionregimen (e.g., network interface 1492 receiving a list of all 45nutraceuticals that can be required by regimen X). User 1460 can usethis information in determining whether regimen X will require anyunusual purchases, for example. In other embodiments, operation 564 canbe performed by circuitry 481 of FIG. 4 or by logic 240 of FIG. 2, insome embodiments.

Operation 566 depicts authenticating a user input (e.g., authenticationlogic 1466 confirming the correctness of a password input by user 1460).In other embodiments, operation 566 can be performed by a system 400that includes circuitry 484 of FIG. 4.

Referring now to FIG. 6, there is shown another example system 600 ableto perform many variants of flow 100 described with reference to one ormore of FIG. 5, 7, 8, 10, 12, or 13. System 600 can be configured toperform these variants with or without proximity or direct interactionwith any user or inventory manager, except those few variants for whichcontext dictates otherwise.

System 600 includes circuitry 650 for registering a dispensation from aninventory within a module 630 for responding to the registering byindicating a request, consistent with flow 100 of FIG. 1. As shown,module 630 can also include one or more of computing device 634, logic636, or logic 638. Circuitry 650 can optionally include one or more oflogic 654, logic 656, or memory 658. Storage 660 can optionally includeone or more of code 667, data 668 (which can comprise historical data orinventory data, e.g.), or other data 670 such as one or more regimens672, 674.

In some embodiments, logic 654 can comprise logic for prompting the testresult (and/or other information that may relate to the subject) byrequesting a test that partly depends on a medical history of thesubject, for example, by transmitting a prompting signal as output 622to network 620. (See FIGS. 11&12.) Alternatively or additionally, system600 can perform a flow 100 including an operation 556, for example,based on a user preference received via input 621 and archived instorage 660.

Referring now to FIG. 7, there are shown various optional features ofoperational flow 100 of FIG. 1 or 5. In various implementations, system600 of FIG. 6 can optionally be configured to perform flow 100 with oneor more of operation 743 or operation 749.

Operation 743 comprises applying one or more inventory maintenancecriteria to the inventory and to the nutraceutical-containingdispensation (e.g., inventory maintenance logic 1447 determining that afamily's current regimen will exhaust the family's annis root innutraceutical bin 1445 in less than a triggering time of two weeks). Thecriteria can likewise include a default or user-specified upper limit ona monetary value of an inventory, for example, or a maximum acceptableage of a perishable nutraceutical-containing compound. In some variantsof the embodiment of FIG. 6, in response to receiving an input 621indicating that a user's inventory manager is nearly full, for example,applying the criteria may accordingly reduce the request quantity toavoid spoilage, substantial investment in an ineffective or unneededregimen, or other forms of waste. Also, system 600 optionally includeslogic 638 comprising logic for querying a user responsive to theregistering (at operation 749), such as by transmitting one or morerequests as output 622 to network 620. This approach can help tailor theregimen by seeking input about a subject when a user is likely to beavailable, for example, around the time of the registering.

Operation 749 comprises querying a user responsive to the registering(e.g., user query logic 1446 sending a request to user 1460 to knowwhether a child still has a flu, to facilitate a decision of whether toreorder).

Operation 754 comprises retrieving at least a portion of the consumptionregimen at least partly based on one or more attributes of a primarysubject (e.g., storage logic 1450 selecting a portion of the contents ofregimen description 1455 based on learning that the primary subject is a6′2″ man who is slightly overweight). In some embodiments, operation 754can include retrieving a regimen (regimen 672 of FIG. 6, e.g.) unique tothe subject. Absent such an individualized regimen, even a fewattributes such as age or symptom can form a basis for an effectiveregimen.

Operation 755 comprises selecting the request quantity partly based onan increment size of an inventory (e.g., quantity determination logic1490 deciding to suggest a second 1-pound tin of herbal tea even when 4single-ounce packets would have been a less costly way to reach a totalof 20 ounces). In other embodiments, data 668 of FIG. 6 may identify theincrement size, for example, used by computing device 634 for performingthe selecting operation 755.

Operation 757 comprises receiving a user input indicating at least oneof a nutraceutical or a symptom (e.g., compound identification logic1496 receiving an indication of a symptom of “having foot cramps” fromsubject description 1453 or user 1460). The user input may be receivedvia a questionnaire (electronic or paper, e.g.), for example.

Operation 758 comprises selecting a nutraceutical at least partly basedon one or more symptoms (e.g., compound identification logic 1496selecting calcium and magnesium citrate responsive to an indication offoot cramps).

Referring now to FIG. 8, there are shown various optional features ofoperational flow 100 of FIG. 1, 5, or 7. In various implementations,system 200 of FIG. 2 or user system 1400 of FIG. 14 can be configured toperform flow 100 with operation 140 including one or more of operation841, operation 843, operation 847, operation 848, or operation 849.

Operation 841 comprises dispensing a nutraceutical (e.g., dispensationconfirmation logic 1443 sending an instruction to nutraceutical bin 1445or to user 1460 via display 1467). In other embodiments, inventorymanager 280 likewise performs operation 841, for example, by dispensinga nutraceutical-containing component 282 responsive to an instruction(via linkage 232) from primary module 210. The registering canoptionally cause or enable or result from the dispensing operation 841,or stand in some other relation to the dispensing operation 841,conditional or otherwise.

Operation 843 comprises combining a mineral with an amino acid (e.g.,regimen implementation logic 1480 implementing a nutraceuticalcombination including an amino acid chelated calcium). In otherembodiments, for a subject who takes a steady regimen including morethan one component (such as these), compound identification logic 1496can optionally streamline regimen implementation by preferringmultivitamins and other products that encapsulate more than one regimencomponent in a single article (tablet, e.g.) or otherwise consolidateconsumption.

Operation 847 comprises registering a received antioxidant-containingcomponent apportioned into one or more capsules (e.g., inventorymaintenance logic 1447 receiving an electronic inventory update to showthat vitamin C capsules have been added to nutraceutical bin 1445).Operation 848 depicts allocating a multivitamin supplement componentapportioned into one or more increments of a uniform increment size(e.g., inventory maintenance logic 1447 reserving all 100 identicaltablets for the use of one person who draws from nutraceutical bin1445). Operation 849 comprises forming the nutraceutical-containingdispensation as a combination containing one or more of the capsules andone or more of the increments (e.g., inventory maintenance logic 1447generating a dispensation specifying two capsules and one tablet, whichdispensation can then be included in a message displayed to user 1460).

FIG. 8 also shows various optional features of operational flow 100 ofFIG. 1, 5, or 7 comprising additional operation 852, operation 854, oroperation 856. In various implementations, system 300 of FIG. 3 or usersystem 1400 of FIG. 4 can be configured to perform flow 100 withoperation 150 including one or more of these additional operations.

Operation 852 comprises receiving a validation of at least a portion ofthe consumption regimen (e.g., network interface 1492 receiving amessage of approval from the subject's doctor concerning a detoxifyingregimen that includes calcium D-glucarate). In some embodiments relatingto FIG. 3, the validation of operation 852 can be received from user 360or expert 314, for example, optionally in response to an automatedrequest for such a validation. The request can define or justify theportion of the consumption regimen briefly, for example, and specify anaction (such as clicking a button or entering a code, e.g.) by which thevalidation can be generated. The responding operation 150 can optionallybe made conditional on receiving the validation before a deadline, forexample, or can otherwise affect a condition or manner by which system300 will complete the responding operation 150.

Operation 854 comprises receiving at least a portion of a health regimenthat includes the consumption regimen (e.g., regimen description 1455receiving a complete diet and exercise regimen). In some variants ofFIG. 3, for example, the portion can be received by circuitry 330 vianetwork 320. System 300 can present several such health regimens ofinterest to user 360 via interface 338, for example, prompting user 360to adopt one or more of the health regimens. Logic 340 can thenimplement one or more user-adopted regimens by storing one or moreinstructions of each of the adopted regimens in medium 350 (a memory,e.g.). Likewise, as will be shown following, system 300 can performoperation 856 before, during, after, or without the above-describedadoption operation. See FIG. 10, for example.

Operation 856 comprises receiving one or more components of theconsumption regimen (e.g., regimen description 1455 receiving a completediet and exercise regimen). Other components of the consumption regimencan optionally be obtained, for example, by deriving them from regimendescription 1455.

Referring now to FIG. 9, there are shown further optional features ofsystem 400 of FIG. 4. As explained above, system 400 comprises circuitry440 for registering a nutraceutical-containing dispensation from aninventory and module 470 for responding to the registering by indicatinga request quantity partly based on the inventory and partly based on aconsumption regimen.

Module 470 optionally comprises display 971 configured for digitallyindicating the request quantity. Alternatively or additionally, module470 can comprise one or more of display 972 configured for graphicallyindicating the request quantity, module 973 for receiving input from auser locally, or module 974 for predicting a state of the inventory.Alternatively or additionally, module 470 can comprise signal-bearingmedium 980 bearing one or more instructions such as those of FIG. 11below.

Also as shown, alternatively or additionally, system 400 can furthercomprise circuitry 981 for accessing a network. Alternatively oradditionally, system 400 can further comprise circuitry 982 fordetermining whether any update can be obtained for the consumptionregimen, circuitry 983 for obtaining a regimen remotely, circuitry 984for communicating with a consultant remotely, circuitry 985 forcommunicating with a supplier, or circuitry 986 for communicating withan inventory manager containing the inventory.

Referring now to FIG. 10, there are shown various optional features ofoperational flow 100 of FIG. 1, 5, 7 or 8. In various implementations,user system 1400 of FIG. 14 or system 400 of FIG. 9 can optionally beconfigured to perform flow 100 with operation 140 including one or moreof operation 1041, operation 1046, operation 1047, operation 1048, oroperation 1049. Operation 1041 comprises accessing a network (e.g., userquery logic 1446 contacting a consultant or other user via theInternet). In other embodiments, operation 1041 is performed bycircuitry 981 in the system 400 as shown in FIGS. 4 & 9.

Operation 1046 comprises receiving input from a user locally (e.g., userquery logic 1446 receiving a query response from user 1460 through userinterface 1462).

Operation 1047 comprises predicting a state of the inventory (e.g.,event predictor 1448 predicting that a supply of zinc in nutraceuticalbin 1445 will run out in 28 days in lieu of restocking or a regimenchange). In some embodiments, operation 1047 can be performed by avariant of system 400 comprising module 974. The prediction may be basedon one or more attributes of one or more dispensations such as theregistered one(s), for example, or upon the consumption regimen or acurrent state of the inventory. The predicted state may be detailed,such as a complete description of each component and its ingredients,its age, its location, and the like. The predicted state mayalternatively be more basic, such as “adequate” or “in need of componentZ.” The predicted state may also be expressed in various forms, such asa duration or a percentage.

Operation 1048 comprises postponing an action responsive to determiningthat the predicted state meets one or more criteria (e.g., scheduler1483 postponing ordering any single item over $200 without a specificapproval from user 1460).

Operation 1049 comprises communicating with an inventory managercontaining the inventory (e.g., dispensation confirmation logic 1443 orinventory maintenance logic 1447 communicating with inventory manager1444 containing an inventory of supplements and medications innutraceutical bin 1445).

Operation 1052 comprises determining whether any alternative,substitute, or other update can be obtained for the consumption regimen(e.g., module update logic 1470 reviewing an accumulation of contentperiodically within or through network interface 1492 to determinewhether the Bone-Up™ regimen has published any updates since lastmonth). The determining can be performed by checking a mailbox, forexample, or otherwise by sending a message into a network such as may bereceived by a server. Making a negative determination can be performedby receiving a negative reply or by waiting a given duration withoutreceiving a reply, for example, or by making some similarly reasonableinference derived from one or more received signals.

Operation 1053 comprises receiving an available regimen remotely (e.g.,network interface 1492 receiving a mark-up language segment relating toat least one nutraceutical from a clinic in another state). Operation1054 comprises adopting the available regimen as the consumption regimen(e.g., module update logic 1470 responding to a user selection bychanging to a simpler regimen).

In some embodiments, system 400 comprises circuitry 983 that can performoperation 1053 by receiving an available regimen in response to arequest or subscription, for example, or may select the availableregimen as a preferable regimen automatically using information aboutthe subject.

Operation 1055 comprises graphically indicating the request quantity(e.g., display 1467 showing a pixel image of two bottles that canobviate a translation or enable a person to understand and approve apurchase without having to read). In some embodiments, display 972performs operation 1055 by showing a first component that is visuallydistinguishable from at least a second component, such as by color orshape.

Operation 1056 comprises digitally indicating the request quantity(e.g., display 1467 showing a default reorder list to a nutraceuticalvendor). Alternatively or additionally, indicating operation 1056 can beperformed by transmitting the request quantity digitally via a conduit(of FIG. 11, e.g.) or a wireless link (of FIG. 3, e.g.).

Referring now to FIG. 11, a system 1100 includes a signal-bearing medium1180 that can comprise (or interact with) a conduit 1120, a disk 1130,an integrated circuit 1140, or a computing device 1150. System 1100 canfurther include a dispenser 1170. Medium 1180 can optionally bear one ormore instructions 1160 comprising at least one of (a) one or moreinstructions for registering a nutraceutical-containing dispensationfrom an inventory and (b) one or more instructions for responding to theregistering by indicating a request quantity partly based on theinventory and partly based on a consumption regimen.

Alternatively or additionally, medium 1180 can bear one or moreinstructions 1162 for recording the nutraceutical-containingdispensation with other medical history data of a subject. The othermedical history data can include one or more prior recordings of adispensation, for example. Alternatively or additionally, medium 1180can bear one or more instructions 1163 for performing thenutraceutical-containing dispensation. Alternatively or additionally,medium 1180 can bear one or more instructions 1164 for prompting thenutraceutical-containing dispensation. Alternatively or additionally,medium 1180 can bear one or more instructions 1165 for detecting thenutraceutical-containing dispensation. Alternatively or additionally,medium 1180 can bear one or more instructions 1166 for determining therequest quantity. Alternatively or additionally, medium 1180 can bearone or more instructions 1168 comprising at least one of (a) one or moreinstructions for receiving an indication of a quantity within each ofone or more delivery units and (b) one or more instructions forindicating the request quantity as a number of the one or more deliveryunits. A given set of one or more instructions can comprise more thanone of instructions 1162-1168, of course, optionally executable bycomputing device 1150.

Referring now to FIG. 12, there are shown various optional features ofoperational flow 100 of FIG. 1, 5, 7, 8, or 10. In variousimplementations, system 1100 of FIG. 11 can optionally be configured toperform flow 100 with operation 140 including one or more of operation1242, operation 1243, operation 1246, operation 1247, or 1249.

Operation 1242 comprises performing the nutraceutical-containingdispensation (e.g., regimen implementation logic 1480 generating adispensation identifying a list of pharmaceuticals and nutraceuticals).In some embodiments, system 1100 performs operation 1242 by transmittinginstructions 1163 via medium 1180 to dispensers 170.

Operation 1243 comprises prompting the nutraceutical-containingdispensation (e.g., regimen implementation logic 1480 causing inventormanager 1444 to perform a physical dispensation immediately). This canlikewise be performed by a computing device 1150, for example, such asby transmitting a dispensing command or by otherwise causing anactuation of a dispenser.

Operation 1246 comprises detecting the nutraceutical-containingdispensation (e.g., dispensation confirmation logic 1443 detecting aphysical dispensation from inventory manager 1444 or a planneddispensation from regimen implementation logic 1480). In anotherexample, operation 1246 can be performed by integrated circuit 1140before, during, after, or without the physical dispensation. Thedispensation to be registered can optionally be conditional, scheduled,or actual.

Operation 1247 comprises responding to a result of a test indicating astate of a subject (e.g., user query logic 1446 receiving a “yes”response after asking the user 1460 whether the subject has a fever). Insome embodiments of system 1100 of FIG. 11, for example, operation 1247can be performed by executing one or more instructions 1166 fordetermining the request quantity.

Operation 1249 comprises recording the nutraceutical-containingdispensation with other medical history data of a subject (e.g., userquery logic 1446 recording the dispensation in subject description1453). In some embodiments, operation 1249 is performed by computingdevice 1150 performing instruction(s) 1162.

Operation 1251 comprises displaying a performance indicator of theregimen relating to a potential result of following the regimen (e.g.,display 1467 can show a comparison between a likelihood of catching aflu with a probiotic-containing yogurt regimen and a similar likelihoodwithout a regimen). The potential result can be tangible, intangible,subjective, objective, or some combination of these. The performanceratio or other indicator can comprise an estimated probability of ameasurable improvement, a ratio of “satisfied” regimen subscribers to“dissatisfied” regimen subscribers, a record of subjective experience,an anecdotal log, a rating, a research summary, a certification, anendorsement, or some other indicator.

Operation 1253 comprises receiving an indication of a quantity withineach of one or more delivery units (e.g., electronic inventory 1456including an indication of a per-unit “dose”). The quantity can be anominal increment of mass (such as milligrams of a vitamin, e.g.), acount (of eggs, e.g.), a length, or some other convenient increment. Insome embodiments, a code module comprising one or more instructions 1166performs operation 1253 before or during operation 1254.

Operation 1254 comprises indicating the request quantity as a number ofthe one or more delivery units (e.g., regimen description 1455describing a regimen as 2 units of item X, et cetera, with item Xdefined only in electronic inventory 1456).

Operation 1255 comprises detecting a condition (e.g., quantitydetermination logic 1490 detecting a user login or other action via userinterface 1462). The condition can comprise a substantially periodicevent, for example, such as an appointment, a day of the month, a timeof day, a mealtime, a work break, or the like. The condition can alsocomprise a storm or other weather condition, a job change or pricechange or other economic event, a smoking habit or some other personalcondition, or any other condition that may affect the subject's life.

The detecting can be triggered by a signal from a calendar program, analarm clock, a sensor, a network event, or a real time trigger, forexample. In some variants of embodiments described above, system 300 ofFIG. 3 performs operation 150 responsive to one or more criteria thatdepend on the detected event(s) as well as the request quantity and theregimen. A care provider can use system 300 to adjust or otherwiseupdate a regimen-implementing request automatically, responsive to ascheduled visit by a patient, for example, if system 300 performsoperation 1256.

Operation 1256 comprises responding to the condition by determining therequest quantity (e.g., quantity determination logic 1490 responding toa user action by refreshing a proposed order by using a current systemtime).

Operation 1258 comprises determining the request quantity partly basedon an indication of a visible attribute or a behavior of a subject(e.g., compound identification logic 1496 and quantity determinationlogic 1490 identifying and ordering a quantity of non-prescriptionlithium responsive to chronic extreme mood swings). The subject, apsychologist, a psychiatrist, a parent, or some other observer mayprovide an objective indication (conscious, e.g.), for example, or asubjective indication (irritable or fatigued, e.g.) of the attribute orbehavior. The request quantity may be zero if the visible attribute orthe behavior indicates a negative reaction by the subject to a componentof that regimen, for example. The indication may relate to a facialattribute (“bags under the eyes,” e.g.), some other skin condition(“rash,” e.g.), or any other visible attribute of a subject.

Operation 1259 comprises indicating the request quantity via a displayof a hand-held device (e.g., display 1467 indicating the quantity via acell phone, a camera, or a hybrid device). In various embodiments, anyof the above-described systems can optionally include a display, forexample. Alternatively or additionally, the system can comprise ahand-held device such as a cell phone, wrist watch or the like.

Referring now to FIG. 13, there are shown various optional features ofoperational flow 100 of FIG. 1, 5, 7, 8, 10, or 12. Operation140—registering a nutraceutical-containing dispensation from aninventory—may include one or more of the following operations: 1341,1342, 1343, 1344, or 1345. Operation 1341 depicts listing one or morenutraceuticals and one or more pharmaceuticals in thenutraceutical-containing dispensation (e.g., regimen implementationlogic 1480 including these items in a displayed or transmitteddispensation). Operation 1342 depicts listing a vitamin and/or a mineralin the nutraceutical-containing dispensation (e.g., regimenimplementation logic 1480 including these items in a displayed ortransmitted dispensation). Operation 1343 depicts listing a protein, anamino acid, an oil, and/or a fat in the nutraceutical-containingdispensation (e.g., regimen implementation logic 1480 including theseitems in a displayed or transmitted dispensation). Operation 1344depicts listing a traditional remedy in the nutraceutical-containingdispensation (e.g., regimen implementation logic 1480 including theseitems in a displayed or transmitted dispensation). Operation 1345depicts receiving a user report of the nutraceutical-containingdispensation (e.g., user query logic 1446 requesting and receiving anotification from user 1460 that the dispensation is planned).

Operation 1360—performing one or more additional operations—may includeone or more of the following operations: 1361, 1362, 1363, 1364, 1366,1368, or

1369. Operation 1361 depicts receiving a request for a subscription(e.g., user interface 1462 receiving a decision that user 1460 issubscribing to the Adkins diet). Operation 1362 depicts obtaining datafrom one or more remote sources (e.g., registration logic receiving theregistration(s) as the obtained data from a nutraceutical bin 1445 thatcan be remote). Operation 1363 depicts obtaining data via a network(e.g., network interface 1492 receiving data via the Internet).

Operation 1364 depicts receiving at least one of a diagnosis or one ormore observations (e.g., subject description 1453 receiving anindication that a particular subject has rheumatoid arthritis).Operation 1366 depicts receiving at least one of a prognosis or anotherprediction (e.g., subject description 1453 receiving an indication thata 2-week convalescence is expected). The diagnosis or prognosis canoptionally be based on one or more test results and/or reports byothers, observations, predictions, reports, history, or otherindications of status. The diagnosis or prognosis may relate to asubject who has adopted the consumption regimen, for example, and maywarrant storing the diagnosis in a medical history. The subject may bediagnosed as having an allergy to seafood, for example, which may bearagainst a fish oil supplement. Substantially the same criterion (“nofish,” e.g.) may effectively become a part of a given subject's regimenin other circumstances as well. It may arise from a received userinstruction or preference (“no fish,” e.g.), a user status (“vegan,”e.g.), or otherwise arise from a received input (via interface 1462,e.g.). The subject may be diagnosed with osteoporosis, as anotherexample, which may bear toward a calcium-containing (or higher-calcium)regimen.

Operation 1368 comprises communicating with a consultant remotely (e.g.,network interface 1492 automatically notifying a subject's dietician ata remote facility). Operation 1369 comprises communicating with asupplier (e.g., network interface 1492 requesting the supplier'savailability and lead times for products of interest). These operationscan generate timely information about the availability or advisabilityof an available regimen, for example, facilitating appropriateadjustments at operation 150. Many embodiments described herein allowfor a more sophisticated and cost-effective approach to building andmaintaining an inventory of effective remedies.

Those having skill in the art will recognize that the state of the arthas progressed to the point where there is little distinction leftbetween hardware and software implementations of aspects of systems; theuse of hardware or software is generally (but not always, in that incertain contexts the choice between hardware and software can becomesignificant) a design choice representing cost vs. efficiency tradeoffs.Those having skill in the art will appreciate that there are variousvehicles by which processes and/or systems and/or other technologiesdescribed herein can be effected (e.g., hardware, software, and/orfirmware), and that the preferred vehicle will vary with the context inwhich the processes and/or systems and/or other technologies aredeployed. For example, if an implementer determines that speed andaccuracy are paramount, the implementer may opt for a mainly hardwareand/or firmware vehicle; alternatively, if flexibility is paramount, theimplementer may opt for a mainly software implementation; or, yet againalternatively, the implementer may opt for some combination of hardware,software, and/or firmware. Hence, there are several possible vehicles bywhich the processes and/or devices and/or other technologies describedherein may be effected, none of which is inherently superior to theother in that any vehicle to be utilized is a choice dependent upon thecontext in which the vehicle will be deployed and the specific concerns(e.g., speed, flexibility, or predictability) of the implementer, any ofwhich may vary. Those skilled in the art will recognize that opticalaspects of implementations will typically employ optically-orientedhardware, software, and or firmware.

The foregoing detailed description has set forth various embodiments ofthe devices and/or processes via the use of block diagrams, flowcharts,and/or examples. Insofar as such block diagrams, flowcharts, and/orexamples contain one or more functions and/or operations, it will beunderstood by those within the art that each function and/or operationwithin such block diagrams, flowcharts, or examples can be implemented,individually and/or collectively, by a wide range of hardware, software,firmware, or virtually any combination thereof. In one embodiment,several portions of the subject matter described herein may beimplemented via Application Specific Integrated Circuits (ASICs), FieldProgrammable Gate Arrays (FPGAs), digital signal processors (DSPs), orother integrated formats. However, those skilled in the art willrecognize that some aspects of the embodiments disclosed herein, inwhole or in part, can be equivalently implemented in integratedcircuits, as one or more computer programs running on one or morecomputers (e.g., as one or more programs running on one or more computersystems), as one or more programs running on one or more processors(e.g., as one or more programs running on one or more microprocessors),as firmware, or as virtually any combination thereof, and that designingthe circuitry and/or writing the code for the software and or firmwarewould be well within the skill of one of skill in the art in light ofthis disclosure. In addition, those skilled in the art will appreciatethat the mechanisms of the subject matter described herein are capableof being distributed as a program product in a variety of forms, andthat an illustrative embodiment of the subject matter described hereinapplies regardless of the particular type of signal bearing medium usedto actually carry out the distribution. Examples of a signal bearingmedium include, but are not limited to, the following: a recordable typemedium such as a floppy disk, a hard disk drive, a Compact Disc (CD), aDigital Video Disk (DVD), a digital tape, a computer memory, etc.; and atransmission type medium such as a digital and/or an analogcommunication medium (e.g., a fiber optic cable, a waveguide, a wiredcommunications link, a wireless communication link, etc.).

While particular aspects of the present subject matter described hereinhave been shown and described, it will be apparent to those skilled inthe art that, based upon the teachings herein, changes and modificationsmay be made without departing from this subject matter described hereinand its broader aspects and, therefore, the appended claims are toencompass within their scope all such changes and modifications as arewithin the true spirit and scope of this subject matter describedherein. Furthermore, it is to be understood that the invention is solelydefined by the appended claims. It will be understood by those withinthe art that, in general, terms used herein, and especially in theappended claims (e.g., bodies of the appended claims) are generallyintended as “open” terms (e.g., the term “including” should beinterpreted as “including but not limited to,” the term “having” shouldbe interpreted as “having at least,” the term “includes” should beinterpreted as “includes but is not limited to,” etc.). It will befurther understood by those within the art that if a specific number ofan introduced claim recitation is intended, such an intent will beexplicitly recited in the claim, and in the absence of such recitationno such intent is present. For example, as an aid to understanding, thefollowing appended claims may contain usage of the introductory phrases“at least one” and “one or more” to introduce claim recitations.However, the use of such phrases should not be construed to imply thatthe introduction of a claim recitation by the indefinite articles “a” or“an” limits any particular claim containing such introduced claimrecitation to inventions containing only one such recitation, even whenthe same claim includes the introductory phrases “one or more” or “atleast one” and indefinite articles such as “a” or “an” (e.g., “a” and/or“an” should typically be interpreted to mean “at least one” or “one ormore”); the same holds true for the use of definite articles used tointroduce claim recitations. In addition, even if a specific number ofan introduced claim recitation is explicitly recited, those skilled inthe art will recognize that such recitation should typically beinterpreted to mean at least the recited number (e.g., the barerecitation of “two recitations,” without other modifiers, typicallymeans at least two recitations, or two or more recitations).Furthermore, in those instances where a convention analogous to “atleast one of A, B, and C, etc.” is used, in general such a constructionis intended in the sense one having skill in the art would understandthe convention (e.g., “a system having at least one of A, B, and C”would include but not be limited to systems that have A alone, B alone,C alone, A and B together, A and C together, B and C together, and/or A,B, and C together, etc.). In those instances where a conventionanalogous to “at least one of A, B, or C, etc.” is used, in general sucha construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, or C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). It will be furtherunderstood by those within the art that any disjunctive word and/orphrase presenting two or more alternative terms, whether in thedescription, claims, or drawings, should be understood to contemplatethe possibilities of including one of the terms, either of the terms, orboth terms. For example, the phrase “A or B” will be understood toinclude the possibilities of “A” or “B” or “A and B.” Moreover, “can”and “optionally” and other permissive terms are used herein fordescribing optional features of various embodiments. These termslikewise describe selectable or configurable features generally, unlessthe context dictates otherwise.

The herein described aspects depict different components containedwithin, or connected with, different other components. It is to beunderstood that such depicted architectures are merely exemplary, andthat in fact many other architectures can be implemented which achievethe same functionality. In a conceptual sense, any arrangement ofcomponents to achieve the same functionality is effectively “associated”such that the desired functionality is achieved. Hence, any twocomponents herein combined to achieve a particular functionality can beseen as “associated with” each other such that the desired functionalityis achieved, irrespective of architectures or intermedial components.Likewise, any two components so associated can also be viewed as being“operably connected,” or “operably coupled,” to each other to achievethe desired functionality. Any two components capable of being soassociated can also be viewed as being “operably couplable” to eachother to achieve the desired functionality. Specific examples ofoperably couplable include but are not limited to physically mateableand/or physically interacting components and/or wirelessly interactableand/or wirelessly interacting components and/or logically interactableand/or logically interacting components.

While certain features of the described implementations have beenillustrated as disclosed herein, many modifications, substitutions,changes and equivalents will now occur to those skilled in the art. Itis, therefore, to be understood that the appended claims are intended tocover all such modifications and changes as fall within the true spiritof the embodiments of the invention.

1. A method comprising: registering a nutraceutical-containing dispensation from an inventory; and responding to the registering by indicating a request quantity partly based on the inventory and partly based on a consumption regimen.
 2. (canceled)
 3. (canceled)
 4. (canceled)
 5. The method of claim 1, wherein responding to the registering by indicating a request quantity partly based on the inventory and partly based on a consumption regimen comprises: receiving a user preference; and identifying a compound comprising the request quantity.
 6. (canceled)
 7. (canceled)
 8. (canceled)
 9. The method of claim 1, wherein responding to the registering by indicating a request quantity partly based on the inventory and partly based on a consumption regimen comprises: receiving the request quantity; and storing the request quantity.
 10. (canceled)
 11. (canceled)
 12. (canceled)
 13. (canceled)
 14. (canceled)
 15. The method of claim 1, further comprising: receiving at least a portion of the consumption regimen.
 16. (canceled)
 17. The method of claim 1, further comprising: receiving a request for a subscription.
 18. (canceled)
 19. (canceled)
 20. (canceled)
 21. (canceled)
 22. The method of claim 1, wherein responding to the registering by indicating a request quantity partly based on the inventory and partly based on a consumption regimen comprises: retrieving at least a portion of the consumption regimen at least partly based on one or more attributes of a primary subject.
 23. (canceled)
 24. The method of claim 1, wherein responding to the registering by indicating a request quantity partly based on the inventory and partly based on a consumption regimen comprises: receiving a user input indicating at least one of a nutraceutical or a symptom.
 25. (canceled)
 26. (canceled)
 27. (canceled)
 28. (canceled)
 29. The method of claim 1, wherein registering a nutraceutical-containing dispensation from an inventory comprises: allocating a multivitamin supplement component apportioned into one or more increments of a uniform increment size.
 30. (canceled)
 31. (canceled)
 32. (canceled)
 33. (canceled)
 34. (canceled)
 35. (canceled)
 36. (canceled)
 37. (canceled)
 38. (canceled)
 39. (canceled)
 40. (canceled)
 41. The method of claim 1, wherein responding to the registering by indicating a request quantity partly based on the inventory and partly based on a consumption regimen comprises: receiving an available regimen remotely; and adopting the available regimen as the consumption regimen.
 42. (canceled)
 43. (canceled)
 44. The method of claim 1, wherein registering a nutraceutical-containing dispensation from an inventory comprises: predicting a state of the inventory.
 45. (canceled)
 46. (canceled)
 47. (canceled)
 48. (canceled)
 49. (canceled)
 50. (canceled)
 51. The method of claim 1, wherein responding to the registering by indicating a request quantity partly based on the inventory and partly based on a consumption regimen comprises: displaying a performance indicator of the regimen relating to a potential result of following the regimen.
 52. (canceled)
 53. The method of claim 1, wherein responding to the registering by indicating a request quantity partly based on the inventory and partly based on a consumption regimen comprises: receiving an indication of a quantity within each of one or more delivery units; and indicating the request quantity as a number of the one or more delivery units.
 54. (canceled)
 55. The method of claim 1, wherein responding to the registering by indicating a request quantity partly based on the inventory and partly based on a consumption regimen comprises: detecting a condition; and responding to the condition by determining the request quantity.
 56. The method of claim 1, wherein responding to the registering by indicating a request quantity partly based on the inventory and partly based on a consumption regimen comprises: determining the request quantity partly based on an indication of a visible attribute or a behavior of a subject.
 57. (canceled)
 58. (canceled)
 59. (canceled)
 60. (canceled)
 61. (canceled)
 62. (canceled)
 63. (canceled)
 64. (canceled)
 65. A system comprising: means for registering a nutraceutical-containing dispensation from an inventory; and means for responding to the registering by indicating a request quantity partly based on the inventory and partly based on a consumption regimen.
 66. (canceled)
 67. (canceled)
 68. (canceled)
 69. (canceled)
 70. (canceled)
 71. The system of claim 65, wherein the means for responding to the registering by indicating a request quantity partly based on the inventory and partly based on a consumption regimen comprises: means for storing the request quantity.
 72. (canceled)
 73. (canceled)
 74. (canceled)
 75. (canceled)
 76. (canceled)
 77. (canceled)
 78. The system of claim 65, wherein the means for registering a nutraceutical-containing dispensation from an inventory comprises: means for applying one or more inventory maintenance criteria to the inventory and to the nutraceutical-containing dispensation.
 79. (canceled)
 80. The system of claim 65, further comprising: means for receiving at least one of a prognosis or another prediction.
 81. The system of claim 65, wherein the means for registering a nutraceutical-containing dispensation from an inventory comprises: means for querying a user responsive to the registering.
 82. The system of claim 65, wherein the means for responding to the registering by indicating a request quantity partly based on the inventory and partly based on a consumption regimen comprises: means for retrieving at least a portion of the consumption regimen at least partly based on one or more attributes of a primary subject.
 83. (canceled)
 84. (canceled)
 85. The system of claim 65, wherein the means for responding to the registering by indicating a request quantity partly based on the inventory and partly based on a consumption regimen comprises: means for selecting a nutraceutical at least partly based on one or more symptoms.
 86. (canceled)
 87. (canceled)
 88. (canceled)
 89. (canceled)
 90. (canceled)
 91. (canceled)
 92. The system of claim 65, wherein the means for responding to the registering by indicating a request quantity partly based on the inventory and partly based on a consumption regimen comprises: means for receiving at least a portion of a health regimen that includes the consumption regimen.
 93. (canceled)
 94. (canceled)
 95. (canceled)
 96. (canceled)
 97. (canceled)
 98. (canceled)
 99. (canceled)
 100. (canceled)
 101. The system of claim 65, wherein the means for responding to the registering by indicating a request quantity partly based on the inventory and partly based on a consumption regimen comprises: means for adopting the available regimen as the consumption regimen.
 102. The system of claim 65, wherein the means for responding to the registering by indicating a request quantity partly based on the inventory and partly based on a consumption regimen comprises: means for graphically indicating the request quantity.
 103. (canceled)
 104. (canceled)
 105. (canceled)
 106. The system of claim 65, wherein the means for registering a nutraceutical-containing dispensation from an inventory comprises: means for performing the nutraceutical-containing dispensation.
 107. The system of claim 65, wherein the means for registering a nutraceutical-containing dispensation from an inventory comprises: means for prompting the nutraceutical-containing dispensation.
 108. (canceled)
 109. The system of claim 65, wherein the means for registering a nutraceutical-containing dispensation from an inventory comprises: means for responding to a result of a test indicating a state of a subject
 110. (canceled)
 111. (canceled)
 112. (canceled)
 113. (canceled)
 114. (canceled)
 115. The system of claim 65, wherein the means for responding to the registering by indicating a request quantity partly based on the inventory and partly based on a consumption regimen comprises: means for determining the request quantity partly based on an indication of a visible attribute or a behavior of a subject.
 116. (canceled)
 117. (canceled)
 118. (canceled)
 119. The system of claim 65, wherein the means for registering a nutraceutical-containing dispensation from an inventory comprises: means for receiving a user report of the nutraceutical-containing dispensation.
 120. A system comprising: circuitry for registering a nutraceutical-containing dispensation from an inventory; and a module for responding to the registering by indicating a request quantity partly based on the inventory and partly based on a consumption regimen.
 121. The system of claim 120, wherein the module for responding to the registering by indicating a request quantity partly based on the inventory and partly based on a consumption regimen comprises: circuitry for determining the request quantity partly based on a user preference.
 122. (canceled)
 123. (canceled)
 124. The system of claim 120, wherein the module for responding to the registering by indicating a request quantity partly based on the inventory and partly based on a consumption regimen comprises: circuitry for confirming the nutraceutical-containing dispensation.
 125. (canceled)
 126. (canceled)
 127. The system of claim 120, further comprising: circuitry for identifying a compound comprising the request quantity.
 128. (canceled)
 129. The system of claim 120, further comprising: circuitry for authenticating a user input.
 130. (canceled)
 131. The system of claim 120, further comprising: circuitry for receiving an update of the module for responding to the registering by indicating a request quantity.
 132. (canceled)
 133. (canceled)
 134. (canceled)
 135. (canceled)
 136. (canceled)
 137. (canceled)
 138. The system of claim 120, further comprising: circuitry for determining whether any update can be obtained for the consumption regimen.
 139. The system of claim 120, further comprising: circuitry for obtaining a regimen remotely.
 140. The system of claim 120, further comprising: circuitry for communicating with a consultant remotely.
 141. (canceled)
 142. The system of claim 120, further comprising: circuitry for communicating with an inventory manager containing the inventory.
 143. (canceled)
 144. (canceled)
 145. (canceled)
 146. A system comprising: a computing device; and at least one of one or more instructions for registering a nutraceutical-containing dispensation from an inventory; and one or more instructions for responding to the registering by indicating a request quantity partly based on the inventory and partly based on a consumption regimen.
 147. (canceled)
 148. (canceled)
 149. (canceled)
 150. (canceled)
 151. The system of claim 146, further comprising: one or more instructions for recording the nutraceutical-containing dispensation with other medical history data of a subject.
 152. (canceled)
 153. (canceled)
 154. (canceled)
 155. (canceled)
 156. The system of claim 146, further comprising: at least one of one or more instructions for receiving an indication of a quantity within each of one or more delivery units; and one or more instructions for indicating the request quantity as a number of the one or more delivery units.
 157. A computer program product comprising: a signal-bearing medium bearing at least one of one or more instructions for registering a nutraceutical-containing dispensation from an inventory; and one or more instructions for responding to the registering by indicating a request quantity partly based on the inventory and partly based on a consumption regimen.
 158. (canceled)
 159. (canceled)
 160. (canceled)
 161. (canceled)
 162. (canceled)
 163. (canceled)
 164. (canceled)
 165. (canceled)
 166. (canceled) 